home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1994 March
/
Internet Info CD-ROM (Walnut Creek) (March 1994).iso
/
inet
/
internet-drafts
/
draft-ietf-x400ops-mhs-service-06.txt
< prev
next >
Wrap
Text File
|
1993-06-07
|
3KB
|
66 lines
RFC 1465:
Title: Routing Coordination for X.400 MHS Services
Within a Multi Protocol / Multi Network
Environment Table Format V3 for Static Routing
Author: D. Eppenberger
Mailbox: Eppenberger@switch.ch
Pages: 31
Characters: 66,833
Updates/Obsoletes: none
The usage of the X.400 Message Handling System (MHS) is growing
rapidly, especially in the commercial world but much interest can also
be found in the academic and research community. New networks and new
addresses come into use each and every day. The underlying technology
for different X.400 networks can vary depending on the transport
network and the X.400 MHS implementations used. As a large number of
X.400 implementations now support multiple stacks, this offers the
chance of implementing a world wide message handling service using the
same electronic mail standard and, therefore, without the need of
gateways with service reduction and without the restriction to a
single common transport network. This, however, leads to several
problems for the MHS manager, two of which are:
- Where do I route new X.400 addresses and
- How do I connect to a MHS domain that uses an underlying
technology that I do not support.
This document proposes short term solutions to these problems.
This memo defines an Experimental Protocol for the Internet
community. Discussion and suggestions for improvement are requested.
Please refer to the current edition of the "IAB Official Protocol
Standards" for the standardization state and status of this protocol.
Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be added
to or deleted from the RFC-DIST distribution list should be sent to
RFC-REQUEST@NIC.DDN.MIL.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to "rfc-info@ISI.EDU" with the message body
"help: ways_to_get_rfcs". For example:
To: rfc-info@ISI.EDU
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to NIC@NIC.DDN.MIL. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU. Please consult RFC 1111, "Instructions to RFC
Authors", for further information.
Joyce K. Reynolds
USC/Information Sciences Institute